In 2018 we marked this extension point for deletion, lets remove it for 2025-03.

Have you checked if the extension-point is used anywhere in the SDK? I remember that quite a number of extensions for deprecated points exit.

This pull request changes some projects for the first time in this development cycle.
Therefore the following files need a version increment:

runtime/features/org.eclipse.core.runtime.feature/feature.xml

An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch.

From 767711d38d5508be524f0551f98f34e8f67090d9 Mon Sep 17 00:00:00 2001
From: Eclipse Platform Bot <platform-bot@eclipse.org>
Date: Sat, 30 May 2026 08:34:11 +0000
Subject: [PATCH] Version bump(s) for 4.41 stream


diff --git a/runtime/features/org.eclipse.core.runtime.feature/feature.xml b/runtime/features/org.eclipse.core.runtime.feature/feature.xml
index 7eddcc12b7..bd0e035c4e 100644
--- a/runtime/features/org.eclipse.core.runtime.feature/feature.xml
+++ b/runtime/features/org.eclipse.core.runtime.feature/feature.xml
@@ -2,7 +2,7 @@
 <feature
       id="org.eclipse.core.runtime.feature"
       label="%featureName"
-      version="1.4.1200.qualifier"
+      version="1.4.1300.qualifier"
       provider-name="%providerName"
       license-feature="org.eclipse.license"
       license-feature-version="0.0.0">
-- 
2.54.0

Further information are available in Common Build Issues - Missing version increments.

Awesome @HannesWell that works. Thank you for the tip

Have you checked if the extension-point is used anywhere in the SDK? I remember that quite a number of extensions for deprecated points exit.

Will do.

Test Results

    54 files  ±0      54 suites  ±0   55m 25s ⏱️ +32s
 4 671 tests ±0   4 649 ✅ ±0   22 💤 ±0  0 ❌ ±0 
11 907 runs  ±0  11 754 ✅ ±0  153 💤 ±0  0 ❌ ±0 

Results for commit 17ff934. ± Comparison against base commit 1223f47.

♻️ This comment has been updated with latest results.

eclipse-platform/eclipse.platform.ui#3936

eclipse-platform/eclipse.platform.ui#3937

#2633

Removals are best done for M1 and not M3

I assume we don’t need two version increment commits.

Failing test requires that I remove ISV doc references to the soon deleted org.eclipse.core.runtime.contentTypes extension point.

The bundle actually lives in the eclipse.platform.releng.aggregator repo, not eclipse.platform.ui

Follow-up after this is merged: org.eclipse.core.contenttype ContentTypeBuilder.getConfigurationElements() explicitly reads both points (lines 243–245 fetch the old org.eclipse.core.runtime.contentTypes). Once the point declaration is gone, registry.getExtensionPoint(...) returns null there, so that branch becomes dead code.

Running my last (grep based) checks on the aggregator now... If that does not find anything I plan to merge, this is loooong in the pipeline.

One place present which can be removed after this is gone, will be done via a separate PR.

// "old" extension point
IExtensionPoint oldPoint = registry.getExtensionPoint(IContentConstants.RUNTIME_NAME, PT_CONTENTTYPES);
if (oldPoint != null) {
    oldConfigElements = oldPoint.getConfigurationElements();
}